Skip to content

Update steamworks to 1.60#5

Merged
Wartori54 merged 2 commits into
EverestAPI:mainfrom
roblabla:update-steamworks
Aug 14, 2025
Merged

Update steamworks to 1.60#5
Wartori54 merged 2 commits into
EverestAPI:mainfrom
roblabla:update-steamworks

Conversation

@roblabla

@roblabla roblabla commented Aug 3, 2025

Copy link
Copy Markdown
Contributor

This, in combination with an update of Steamworks.NET in Everest, will allow modders to use the newer features offered by the latest version of the Steamworks SDK.

This removes CSteamworks.dll, as it is unnecessary with the newer versions of Steamworks.NET/steam_api, as steam_api provides its own C wrapper nowadays.

@roblabla roblabla force-pushed the update-steamworks branch 2 times, most recently from 6a9a561 to cbd0381 Compare August 3, 2025 13:59

@Wartori54 Wartori54 left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This project's goal is to avoid having binary blobs in the repository as much as possible. With steam_api it still has to be shipped this way, but for Steamworks.NET it should be built in CI (just like the other C# projects) instead of being bundled like steam_api.
In this case, though, it would be also fine if the release from the Steamworks.NET repository is pulled and the binaries in there used in CI.
Make sure to note this on "Open-Source Libraries" part in the README.md

@roblabla roblabla force-pushed the update-steamworks branch 6 times, most recently from 66bd91f to 2721040 Compare August 4, 2025 22:27
@roblabla

roblabla commented Aug 4, 2025

Copy link
Copy Markdown
Contributor Author

I added a Steamworks.NET submodule in the source directory (initialized at 2024.8.0), added it to the README, and built it in CI.

@psyGamer

psyGamer commented Aug 5, 2025

Copy link
Copy Markdown
Member

Since the native libraries are already vendored by the Steamworks.NET project, I think we should just copy them from their repo to avoid the possibility of the versions getting desynced.

@roblabla

roblabla commented Aug 5, 2025

Copy link
Copy Markdown
Contributor Author

Ah, I hadn't realized that they were, but you're right. They're in the com.rlabrecque.steamworks.net/Plugins folder.

I'll adapt the CI to copy the binaries from there.

@roblabla roblabla force-pushed the update-steamworks branch from 2721040 to b77df01 Compare August 5, 2025 12:22
@roblabla

roblabla commented Aug 5, 2025

Copy link
Copy Markdown
Contributor Author

All fixed, we now copy the steam_api files found within the Steamworks.NET submodule, ensuring they are kept in sync.

@Wartori54 Wartori54 left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM other than that minor nitpick

Comment thread .github/workflows/build-libs.yml Outdated
This, in combination with an update of Steamworks.NET, will allow
modders to use the newer features offered by the latest version of the
Steamworks SDK.
@roblabla roblabla force-pushed the update-steamworks branch from b77df01 to c108ad1 Compare August 5, 2025 16:18

@psyGamer psyGamer left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Also LGTM.
Tho note that the double-space in MarkDown files indicate a new line and are not incorrect trailing whitespace. I've just fixed it myself since its trivial, but it would be good to remember in the future.

@roblabla

roblabla commented Aug 5, 2025

Copy link
Copy Markdown
Contributor Author

Oh, that's my editor remoing trailing whitespace. I should probably configure that to ignore Markdown files ^^'

@Wartori54 Wartori54 merged commit 3311fc9 into EverestAPI:main Aug 14, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants